Skip to content

bundle: warn when a workspace path is in /Workspace/Shared without users CAN_MANAGE#5428

Draft
shreyas-goenka wants to merge 1 commit into
mainfrom
ticklish-munching-bear
Draft

bundle: warn when a workspace path is in /Workspace/Shared without users CAN_MANAGE#5428
shreyas-goenka wants to merge 1 commit into
mainfrom
ticklish-munching-bear

Conversation

@shreyas-goenka
Copy link
Copy Markdown
Contributor

@shreyas-goenka shreyas-goenka commented Jun 3, 2026

Summary

Warns when a workspace path is configured under /Workspace/Shared — which grants read/write access to all workspace users — without the top-level permissions section declaring that broad access via group_name: users with CAN_MANAGE.

Renames ValidateSharedRootPermissionsValidateWorkspaceSharedPermissions and extends it from root_path-only to also cover state_path:

  1. root_path in /Workspace/Shared without users: CAN_MANAGE
  2. state_path in /Workspace/Shared without users: CAN_MANAGE

The state_path warning is suppressed only when state_path is nested under root_path (the root warning already covers it). When state_path is a separate shared folder, both warnings fire.

Independent of the telemetry PR (#5440) and the deploy-time live-ACL check (#5439).

@eng-dev-ecosystem-bot
Copy link
Copy Markdown
Collaborator

eng-dev-ecosystem-bot commented Jun 3, 2026

Commit: 00c5b7b

Run: 27009288114

@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from e7e9e83 to 60fba4e Compare June 4, 2026 11:42
@shreyas-goenka shreyas-goenka changed the title bundle: warn when state_path uses /Workspace/Shared and add telemetry for state path scope bundle: warn on /Workspace/Shared workspace paths and add permission-scope telemetry Jun 4, 2026
@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from 60fba4e to cc47397 Compare June 4, 2026 11:49
@shreyas-goenka shreyas-goenka changed the title bundle: warn on /Workspace/Shared workspace paths and add permission-scope telemetry bundle: warn when a workspace path is in /Workspace/Shared without users CAN_MANAGE Jun 4, 2026
@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from cc47397 to b2c7271 Compare June 5, 2026 10:05
@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from b2c7271 to c2aa303 Compare June 5, 2026 10:11
@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from c2aa303 to b1d732b Compare June 5, 2026 10:14
@shreyas-goenka shreyas-goenka force-pushed the ticklish-munching-bear branch from b1d732b to 9e2f26b Compare June 5, 2026 10:18
…ers CAN_MANAGE

Renames ValidateSharedRootPermissions to ValidateWorkspaceSharedPermissions and
extends it to also cover workspace.state_path. It warns when root_path or state_path
is in /Workspace/Shared — granting read/write to all workspace users — but the
top-level permissions section does not declare that access via group_name: users
CAN_MANAGE.

The state_path warning is suppressed only when state_path is nested under root_path,
since the root warning already covers it. When state_path is a separate shared
folder, both warnings fire.

Co-authored-by: Shreyas Goenka <shreyas.goenka@databricks.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants